Preview deployment for your docs. Learn more about Mintlify Previews.

Gonna spam comments, feel free to resolve!

Not exactly. Looking at the actual code:

1. No default export required — The ADK uses expandExports to scan all named exports from conversation files (line 860-866), not just default. The
   example in lack uses a named export (export const AllChat), not export default.
2. Auto-discovery is true — The ADK does scan all .ts/.js files in the conversations directory, checks each export with
   Primitives.Definitions.isConversationDefinition(), and registers any that are valid Conversation instances (lines 888-915).

Actions are also callable from outside the agent via the Botpress API.

The generated AdkClient (client-wrapper.ts:346-358) wraps client.callAction() — which is a Botpress API call. So any external system with a valid bot
client can invoke actions the same way:

client.callAction({ type: 'lookupOrder', input: { orderId: '123' } })

Additionally, adk run scripts can call actions from outside the normal agent runtime (via the actions proxy in actions.ts, which also uses
client.callAction for integration actions).

So the accurate statement would be: Actions are callable from workflows, conversations, other actions, external API clients, and ADK scripts.

Would be nice to tie into Control Panel Stuff with the primitives:
i.e.

Invoking / testing actions and workflows from the control panel
interacting with tables on dev and prod in the tables view, managing sync status and sync requests,
etc

would be nice to also introduce them to the agentsteps screen here.

Gonna spam comments, feel free to resolve!

Not exactly. Looking at the actual code:

1. No default export required — The ADK uses expandExports to scan all named exports from conversation files (line 860-866), not just default. The
   example in lack uses a named export (export const AllChat), not export default.
2. Auto-discovery is true — The ADK does scan all .ts/.js files in the conversations directory, checks each export with
   Primitives.Definitions.isConversationDefinition(), and registers any that are valid Conversation instances (lines 888-915).

Good catch, fixed! Updated to say the ADK discovers all exported Conversation instances (default or named).

Actions are also callable from outside the agent via the Botpress API.

The generated AdkClient (client-wrapper.ts:346-358) wraps client.callAction() — which is a Botpress API call. So any external system with a valid bot client can invoke actions the same way:

client.callAction({ type: 'lookupOrder', input: { orderId: '123' } })

Additionally, adk run scripts can call actions from outside the normal agent runtime (via the actions proxy in actions.ts, which also uses client.callAction for integration actions).

So the accurate statement would be: Actions are callable from workflows, conversations, other actions, external API clients, and ADK scripts.

Fixed!

Would be nice to tie into Control Panel Stuff with the primitives: i.e.

Invoking / testing actions and workflows from the control panel interacting with tables on dev and prod in the tables view, managing sync status and sync requests, etc

Noted! Will add these cross references as soon as add the control panel page!

we should prompt them to open up the control panel earlier.
would be nice to also introduce them to the agentsteps screen here.

No evals yet in this release! We can wait it till next release to add it!

we should prompt them to open up the control panel earlier.
would be nice to also introduce them to the agentsteps screen here.

Good suggestions! I moved the control panel above adk chat, also include a screenshot for agent steps.

Should this be part of project structure?

I put it here as a quick intro since it ties to agent.config.ts. But the full deep dive will be in the dedicated State and Configuration pages which I'm gonna add in the next PR.